Changes between Version 12 and Version 13 of Protocol Specific Questions

Timestamp:

Jul 4, 2007, 5:47:39 PM (17 years ago)

Author:

John Bailey

Comment:

Some minor tweaks to reflect reality, stop some bad WikiLinks? and rephrase the Sametime questions as actual questions

Protocol Specific Questions

@@ -35 +35 @@
 
 === Why do my buddies' messages display incorrectly? ===
-ICQ has no comprehension of character sets or encodings.  It simply sends (almost) any random chunk of data a user enters.  Pidgin by default assumes everything is UTF-8.  If this is not the case, you will need to edit your account (Accounts->''your ICQ account''->Edit Account) and change the Encoding setting on the Advanced tab.  You will need to enter the correct encoding for your buddies' messages there.  You can specify multiple encodings in a comma-delimited list, such as `UTF-8,ISO-8859-15`, to cause Pidgin to attempt multiple encodings.  In this case, each encoding is tried in succession until a successful decode happens or all encodings listed are exhausted.
+ICQ has no comprehension of character sets or encodings.  It simply sends (almost) any random chunk of data a user enters.  Pidgin by default assumes everything is UTF-8.  If this is not the case, you will need to edit your account (Accounts->''your ICQ account''->Edit Account) and change the Encoding setting on the Advanced tab.  You will need to enter the correct encoding for your buddies' messages there.  At this time it is currently possible to configure only one encoding for an ICQ account.
 
 == IRC Protocol ==
@@ -250 +250 @@
 == Novell Groupwise Messenger Protocol ==
 
-GroupWise Messenger is a component of GroupWise see [http://www.novell.com/products/groupwise http://www.novell.com/products/groupwise]
+Novell !GroupWise Messenger is a component of Novell !GroupWise see [http://www.novell.com/products/groupwise http://www.novell.com/products/groupwise]
 
 === Are there any public servers? ===
-Not really.  This protocol is designed to connect to a GroupWise Messenger server running on a corporate LAN.  No one that we're aware of runs a public server.
+Not really.  This protocol is designed to connect to a Novell !GroupWise Messenger server running on a corporate LAN.  No one that we're aware of runs a public server.
 
 === I can't seem to get it to work. ===
-Novell tells us that this protocol plugin will only work with either the GroupWise Messenger for Linux server or the GroupWise Messenger SP2 (or higher) server for NetWare and Windows.  In addition, the server must be secure (SSL enabled).  If you have any trouble, see the FAQ question about submitting bugs, and they will be forwarded to Novell, who have been kind enough to continue active maintenance to the protocol plugin code they provided us.
+Novell tells us that this protocol plugin will only work with either the !GroupWise Messenger for Linux server or the !GroupWise Messenger SP2 (or higher) server for !NetWare and Windows.  In addition, the server must be secure (SSL enabled).  If you have any trouble, see the FAQ question about submitting bugs, and they will be forwarded to Novell, who have been kind enough to continue active maintenance of the protocol plugin code they provided us.
 
 == Lotus Sametime Protocol ==
@@ -263 +263 @@
 Apart from a demonstration server hosted by Lotus, no. This protocol is designed to connect to a Lotus Sametime server running on a corporate LAN.
 
-=== I cannot add a Lotus Sametime account to Pidgin ===
+=== Why doesn't Sametime appear in the protocols list? ===
 Sametime support in Pidgin depends on a separate library called Meanwhile. You will need to install both the Meanwhile library and the libpurple-meanwhile package to enable Sametime support. If you are building Pidgin from source, then libpurple-meanwhile will be built automatically if you have the development headers for Meanwhile installed.
 
-=== I'm getting an error "Not Authorized" when attempting to connect ===
+=== Why do I get the error "Not Authorized" when connecting? ===
 The Sametime server to which you're attempting to connect has been configured with a white-list of acceptable clients. This error indicates that the client ID used by Pidgin (0x1700) is apparently not in that white-list, so the server is not permitting you to log in. You can cause Pidgin to masquerade as the default Sametime Connect client by setting the "Hide client identity" option in your account preferences.